Edit-share broken in DOORS 961

I recently received notice of APAR PI64773: DOORS CHANGES MADE TO OBJECTS IN SHAREABLE EDIT MODE ARE LOST, which indicates that concurrent editing in a module in DOORS 9.6.1.x cannot be trusted.  No error is displayed when shareable-edit changes are lost.

Does anyone have plans for how to deal with this issue?

I don't see any good options:

- Preventing shareable-edit by removing specific access rights to all objects is time-consuming and difficult to enforce on a large scale

- Reverting to pre-961 DOORS gives up needed capabilities and fixes.

- Asking users to only use exclusive-edit mode is unrealistic given program deadlines

 


RogerGallion - Tue Jun 28 08:34:52 EDT 2016

Re: Edit-share broken in DOORS 961
kourosh - Thu Jun 30 18:33:44 EDT 2016

An APAR was identified  for a very specific scenario that as far as we know has not been reported by other customers at this point. This APAR will be resolved in an upcoming DOORS release and anyone who has any questions should contact IBM Support.

Re: Edit-share broken in DOORS 961
RogerGallion - Fri Jul 01 08:04:55 EDT 2016

Interesting.  The APAR PI64773 seems to be gone this morning (returns a '410 Gone' status).  Yet when I received an email notification from IBM on the issue on 6/27/2016 (citing link http://www-01.ibm.com/support/docview.wss?uid=swg1PI64773&myns=apar&mynp=DOCTYPEstatus&mync=E&cm_sp=apar-_-DOCTYPEstatus-_-E), the APAR description gave no indication it was for a very specific scenario.

 

Shall we pretend this APAR never happened?

Re: Edit-share broken in DOORS 961
smarti.sj - Tue Jul 05 09:04:48 EDT 2016

RogerGallion - Fri Jul 01 08:04:55 EDT 2016

Interesting.  The APAR PI64773 seems to be gone this morning (returns a '410 Gone' status).  Yet when I received an email notification from IBM on the issue on 6/27/2016 (citing link http://www-01.ibm.com/support/docview.wss?uid=swg1PI64773&myns=apar&mynp=DOCTYPEstatus&mync=E&cm_sp=apar-_-DOCTYPEstatus-_-E), the APAR description gave no indication it was for a very specific scenario.

 

Shall we pretend this APAR never happened?

I noticed it was gone as well - I would definitely like to know more on the specifics of the issue.

Re: Edit-share broken in DOORS 961
mstanke - Fri Jul 08 03:51:21 EDT 2016

Hello,

The APAR PI64773 was revoked. The issue was identified for a specific scenario using a DOORS version uncluding specific testfixes which were only provided to that one customer.
In all our GA releases this issue was not seen.

Feel free to try the associated use case in your environment:

User 1
1. Open Module (Read Only to start)
2. Go to Edit -> Shareable
3. Go to Object and locks the object
4. Make the changes to the attribute value

User 2
1a. Open Module (Read Only to start)
2a. Go to Edit -> Shareable
3a. Make a change to different object changing the attribute value
------
Now let both users save the changes, unlock the object and close the module
------
The result of that particular issue was:
The user who did File > Save and Unlock last was saved.
However, the user who hit first save, the data was loss.

Re: Edit-share broken in DOORS 961
RogerGallion - Fri Jul 08 07:10:41 EDT 2016

mstanke - Fri Jul 08 03:51:21 EDT 2016

Hello,

The APAR PI64773 was revoked. The issue was identified for a specific scenario using a DOORS version uncluding specific testfixes which were only provided to that one customer.
In all our GA releases this issue was not seen.

Feel free to try the associated use case in your environment:

User 1
1. Open Module (Read Only to start)
2. Go to Edit -> Shareable
3. Go to Object and locks the object
4. Make the changes to the attribute value

User 2
1a. Open Module (Read Only to start)
2a. Go to Edit -> Shareable
3a. Make a change to different object changing the attribute value
------
Now let both users save the changes, unlock the object and close the module
------
The result of that particular issue was:
The user who did File > Save and Unlock last was saved.
However, the user who hit first save, the data was loss.

Thanks for the detailed explanation.  But why was APAR PI64773 revoked, since it is a real issue?  It would have been better to include the information you provided in the APAR description.  As it stands now, there are probably hundreds of users who received a notification email from IBM on this APAR and when they follow the link provided in the notification email they just get a "410 Gone" error.

Re: Edit-share broken in DOORS 961
mstanke - Fri Jul 08 07:22:05 EDT 2016

RogerGallion - Fri Jul 08 07:10:41 EDT 2016

Thanks for the detailed explanation.  But why was APAR PI64773 revoked, since it is a real issue?  It would have been better to include the information you provided in the APAR description.  As it stands now, there are probably hundreds of users who received a notification email from IBM on this APAR and when they follow the link provided in the notification email they just get a "410 Gone" error.

It was revoked because it is not a real issue. This issue does not occur in any GA release of DOORS. It was only related to very specific testfix which itself was only provided to one customer.
I've forwarded the information to update the link.

Re: Edit-share broken in DOORS 961
RogerGallion - Fri Jul 08 07:25:06 EDT 2016

mstanke - Fri Jul 08 07:22:05 EDT 2016

It was revoked because it is not a real issue. This issue does not occur in any GA release of DOORS. It was only related to very specific testfix which itself was only provided to one customer.
I've forwarded the information to update the link.

Thanks.